Information extraction apparatus, and automatic firmware update system and method for embedded system

ABSTRACT

An automatic firmware update method for an embedded system includes establishing wireless communication between an application layer of the embedded system and a remote server, detecting a version of firmware stored in the remote server corresponding to the embedded system while the wireless communication is established, downloading the firmware in a new version and an update policy when the firmware in the new version is available, storing the downloaded firmware in the new version and the downloaded update policy in a storage unit, issuing an update notification according to an update object of the downloaded firmware in the new version, reading the update policy according to the update notification, and performing an update procedure for updating the firmware to the new version according to the read update policy.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority from U.S. Patent Application Ser. No.62/738,201 filed on Sep. 28, 2018, the entire disclosure of which ishereby incorporated by reference.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to an information extraction apparatus,and an automatic firmware update method for an embedded system and anautomatic firmware update system thereof.

Description of the Prior Art

Firmware is a type of software embedded in a hardware device, and isusually located in a flash memory or a read-only memory (ROM) in anapplication-specific integrated circuit (ASIC) or a programmable logicdevice (PLD). Firmware is extensively applied in electronic products,and achieves an intended designed function by collaborative operationsestablished between software and hardware using firmware designed by adeveloping manufacturer of an electronic product. Further, before anelectronic product is shipped out of the factory, the foregoingdeveloping manufacturer also conducts tests on the electronic product toverify whether the electronic product is functional. If any abnormalityis discovered during the verification process, debugging needs to beperformed to ensure that the electronic product can operate normallyafter it is sold to a consumer.

However, with the ever-increasingly complicated functions of currentelectronic products, it is extremely difficult to verify all functionsduring a development process, and some errors not found during thedevelopment phase may be discovered after actual use of consumers. Atthis point in time, firmware in the electronic products needs to bemodified, that is, firmware needs to be updated, in order to correct theerrors. Therefore, a user of the electronic products needs toinitiatively find the corresponding electronic product from a webpage ofa developing manufacturer or a vendor of the electronic product to checkif an updated version of the firmware is available. If the manufactureror vendor releases the firmware in a new version, the user needs toinitiatively download the firmware in the new version to the electronicproduct to perform update of the firmware, and the user cannot use theelectronic product during the update procedure, hence causinginconvenience.

SUMMARY OF THE INVENTION

In one embodiment, an automatic firmware update method for an embeddedsystem includes establishing wireless communication between anapplication layer of the embedded system and a remote server, detectinga version of firmware stored in the remote server corresponding to theembedded system while the wireless communication is established,downloading the firmware in a new version and an update policy when thefirmware in the new version is available, storing the downloadedfirmware in the new version and the downloaded update policy in astorage unit, issuing an update notification according to an updateobject of the downloaded firmware in the new version, reading the updatepolicy according to the update notification, and performing an updateprocedure for updating the firmware to the new version according to theread update policy.

In one embodiment, an information extraction apparatus includes a cameracomponent, a storage unit, a network module and a processing unit. Thecamera component captures an ambient environment to generate anenvironment image stream presenting the ambient environment. The storageunit stores the environment image stream. The processing unit is coupledto the storage unit and the network module. The processing unit includesan application layer and a middleware. The application layer detects aversion of firmware stored in a remote server corresponding to theembedded system by using the network module, and downloads and storesthe firmware in a new version and an update policy in a storage unitwhen the firmware in the new version is available. The middleware readsthe update policy upon receipt of an update notification from theapplication layer, and performs an update procedure for updating thefirmware to the new version according to the update policy.

In one embodiment, an automatic firmware update system for an embeddedsystem includes a storage unit, an application layer and a middleware.The application layer establishes wireless communication with a remoteserver, detects a version of firmware stored in the remote servercorresponding to the embedded system while the wireless communication isestablished, downloads the firmware in a new version and an updatepolicy when the firmware in the new version is available, stores thedownloaded firmware in the new version and the downloaded update policyin a storage unit, and issues an update notification according to anupdate object of the firmware in the new version. The middlewarereceives the update notification from the application layer, reads theupdate policy upon receipt of the update notification, and performs anupdate procedure for updating the firmware to the new version accordingto the update policy.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an embedded system according to anembodiment of the present invention;

FIG. 2 is a flowchart of an automatic firmware update method for anembedded system according to an embodiment of the present invention;

FIG. 3 is a flowchart of another embodiment of the automatic firmwareupdate method in FIG. 2;

FIG. 4 is a flowchart of yet another embodiment of the automaticfirmware update method in FIG. 2;

FIG. 5 is a block diagram of another embodiment of the embedded systemin FIG. 1;

FIG. 6 is a block diagram of yet another embodiment of the embeddedsystem in FIG. 1; and

FIG. 7 is a block diagram of an implementation of an informationextraction apparatus according an embodiment of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

FIG. 1 shows a block diagram of an embedded system according to anembodiment of the present invention. Referring to FIG. 1, the embeddedsystem 1 includes an automatic firmware update system 10. The automaticfirmware update system 10 can be connected via wireless communication toa remote server 2 having therein a firmware in a version correspondingto the embedded system 1, and can perform an update procedure forupdating the firmware of the embedded system 1 to a new version.

The automatic firmware update system 10 of the embedded system 1includes an application layer 11, a middleware 12 connected to theapplication layer 11, and a storage unit 15. The application layer 11can wirelessly communicate with the remote server 2 to detect theversion of firmware stored in the remote server 2 corresponding to theembedded system 1, and determine whether to perform an update procedurefor updating the firmware in the embedded system 1 to a new versionaccording to whether the version of the firmware is updated to the newversion.

Refer to FIG. 1 and FIG. 2. FIG. 2 shows a flowchart of an automaticfirmware update method for an embedded system according to an embodimentof the present invention. During an operation, the application layer 11first establishes wireless communication therefrom with the remoteserver 2 (step S01). While the wireless communication is established,the version of firmware stored in the remote server 2 corresponding tothe embedded system 1 is detected by the application layer 11 (step S02)to determine whether the version of the firmware stored in the remoteserver 2 corresponding to the embedded system 1 is updated. For example,the application layer 11 can compare whether the version number for thefirmware currently run in the embedded system 1 is the same as theversion number of the firmware stored in the remote server 2corresponding to the embedded system 1, so as to determine whether thereis a new version for the firmware stored in the remote server 2corresponding to the embedded system 1. When the application layer 11determines that a new version of the firmware is released and available(the determination result is “yes”), the application layer 11 downloadsthe firmware in the new version and an update policy from the remoteserver 2 (step S03), and stores the downloaded firmware in the newversion and the downloaded update policy in the storage unit 15 (stepS04). Further, the application layer 11 issues an update notification tothe middleware 12 according to an update object of the firmware in thenew version (step S05), and the middleware 12 reads the update policyfrom the storage unit 15 according to the update notification (step S06)and then determines whether the update policy is satisfied (step S07).When the update policy is satisfied (the determination result is “yes”),it means that an update procedure for updating the firmware to the newversion can be currently performed, and the middleware 12 starts theupdate procedure for updating firmware to the new version (step S08).

Thus, a developing manufacturer of the embedded system 1 can define anupdate policy, and upload the firmware in the new version and thedefined update policy to the remote server 2. The automatic firmwareupdate system 10 can automatically download the firmware in the newversion from the remote server 2 and automatically perform the updateprocedure for updating the firmware to the new version when the updatepolicy is satisfied. A user of the embedded system 1 is not required toinitiatively determine whether the version of the firmware in theembedded system 1 is updated or manually download the firmware in thenew version from the remote server 2, nor is the user required tocontemplate when is the best timing for performing the update procedurefor updating the firmware to the new version. As such, the ease of useof the embedded system 1 is immensely enhanced, and the version of thefirmware in the embedded system 1 is constantly kept in the latestversion so as to improve the stability of the embedded system 1.

In some embodiments, the remote server 2 has a mapping table (as shownin Table—1) stored therein. The mapping table records multiple updatepolicies and current versions of the firmware of multiple embeddedsystems 1 supported by the remote server 2 and defined by a developingmanufacturer. Accordingly, when wireless communication is establishedbetween the embedded system 1 and the remote server 2, the automaticfirmware update system 10 can automatically look up the mapping tablestored in the remote server 2, and determine whether update needs to beperformed according to the corresponding update policy and the currentversion of the firmware in the mapping table, so as to furtherautomatically download the firmware in the new version from the remoteserver 2 and to automatically perform the update procedure for updatingthe firmware to the new version when the update policy is satisfied.

TABLE 1 Version of firmware Type of device^(#) Update policy 0.1 51111.xml 2.2 5 000.xml 0.5 5 333.xml ^(#)The evolution type of thedevice in the embedded system 1, e.g., a 5th-generation product.

In one embodiment, when the update policy is not satisfied (thedetermination result is “no”), the middleware 12 can wait for a timeperiod (step S11) and again determine whether the update policy issatisfied once the time period ends. For example, the time period can be30 seconds, that is, the middleware 12 can determine once every 30seconds after receiving the update notification whether the updatepolicy is satisfied.

Furthermore, the update policy can be when the embedded system 1 is in anon-low power state or when the embedded system 1 is not performing datasynchronization with the remote server 2. More specifically, when theembedded system 1 is in a low power state or when the embedded system 1is performing data synchronization with the remote server 2, theautomatic firmware update system 10 does not perform the updateprocedure for updating the firmware to the new version; only when theembedded system 1 exits the low power state or the data synchronizationwith the remote server 2 is terminated, the automatic firmware updatesystem 10 then starts the update procedure for updating the firmware tothe new version. Thus, issues of shutting down of the embedded system 1caused by insufficient power during the update procedure for updatingthe firmware to the new version and hence malfunction of the embeddedsystem 1 due to incomplete firmware update, or data loss caused byinterrupted data synchronization between the embedded system 1 and theremote server 2 as a result of the update procedure for updating thefirmware to the new version, can be avoided.

In one embodiment, the update object of updating the firmware to the newversion can be execution firmware of the entire embedded system 1, thatis, the embedded system 1 needs to be rebooted after the updateprocedure of the execution firmware is complete. Accordingly, as shownin FIG. 1, the automatic firmware update system 10 of the embeddedsystem 1 further includes a kernel 13 and a bootloader 14. The kernel 13is connected between the middleware 12 and the bootloader 14. During anoperation, referring to FIG. 1 and FIG. 3, when the update policy readby the middleware 12 according to the update notification is satisfied,in step S08, the middleware 12 reads the stored firmware in the newversion from the storage unit 15 (step S081), updates the executionfirmware of the embedded system 1 according to the read firmware in thenew version (step S082), and outputs a reboot instruction after theexecution firmware of the embedded system 1 is updated completely (stepS083). The kernel 13 receives the reboot instruction from the middleware12 after the execution firmware of the embedded system 1 is updatedcompletely (step S09), and executes the reboot instruction to enable thebootloader 14 to perform a reboot procedure of the embedded system 1(step S10), allowing the embedded system 1 to reboot and operateaccording to the firmware in the new version after the executionfirmware thereof is updated completely, thus completing the updateprocedure for the execution firmware of the embedded system 1.

In another embodiment, the update object of updating the firmware to thenew version can also be only the execution firmware of the applicationlayer 11; that is to say, after the update procedure for the executionfirmware of the application layer 11 is complete, only the applicationlayer 11 needs to be shut down instead of rebooting the embedded system1. Correspondingly, referring to FIG. 1 and FIG. 4, when the updatepolicy read by the middleware 12 according to the update notification issatisfied, in step S08, the middleware 12 reads the stored firmware inthe new version from the storage unit 15 (step S081), the middleware 12subsequently shuts down the application layer 11 (step S084), and afterthe application layer 11 is shut down, the middleware 12 updates theexecution firmware of the application layer 11 according to the readfirmware in the new version (step S085), thus completing the updateprocedure for the execution firmware of the application layer 11. Theapplication layer 11 is again activated after being shut down, andoperates according to the updated firmware in the new version.

FIG. 5 shows a block diagram of another embodiment of the embeddedsystem in FIG. 1. As shown in FIG. 5, the embedded system 1 furtherincludes a network management element 111 controlled by the applicationlayer 11 and a service element 121 controlled by the middleware 12, andthe update procedure for the execution firmware of the application layer11 can be performed by the network management element 111 and theservice element 121. More specifically, referring to FIG. 4 and FIG. 5,the network management element 111 first establishes wirelesscommunication therefrom with the remote server 2 (step S01). While thewireless communication is established, the network management element111 determines whether the remote server 2 has the firmware in the newversion corresponding to the embedded system 1 (step S02). When it isdetermined that the firmware in the new version is available in theremote server 2, the network management element 111 downloads thefirmware in the new version and an update policy from the remote server2 (step S03), and stores the firmware in the new version and the updatepolicy in the storage unit 15 (step S04). The network management element111 then sends an update notification to the service element 121controlled by the middleware 12 (step S05), and the service element 121reads the update policy according to the update notification (step S06)and determines whether the update policy is satisfied. When the updatepolicy is satisfied, in step S08, the service element 121 reads thestored firmware in the new version from the storage unit 15 (step S081),shuts down the application layer 11 (step S084), and updates theexecution firmware of the application layer 11 after the applicationlayer 11 is shut down (step S085), thereby completing the updateprocedure for the execution firmware of the application layer 11 by thenetwork management element 111 and the service element 121.

FIG. 6 shows a block diagram of yet another embodiment of the embeddedsystem in FIG. 1. As shown in FIG. 6, the embedded system 1 furtherincludes an event control element 131 controlled by the kernel 13 and amicro control element 141 controlled by the bootloader 14. By thenetwork management element 111, the service element 121, the eventcontrol element 131 and the micro control element 141, the updateprocedure for the execution firmware of the entire embedded system 1 canbe carried out. More specifically, referring to FIG. 3 as well as FIG.6, the network management element 111 first establishes wirelesscommunication therefrom with the remote server 2 (step S01). While thewireless communication is established, the network management element111 determines whether the remote server 2 has firmware in a new versioncorresponding to the embedded system 1 stored therein (step S02). Whenit is determined that the firmware in the new version is present at theremote server 2, the network management element 111 downloads thefirmware in the new version and an update policy from the remote server2 (step S03), stores the firmware in the new version and the updatepolicy in the storage unit 15 (step S04), and then sends an updatenotification to the service element 121 controlled by the middleware 12(step S05). The service element 121 then reads the update policyaccording to the update notification (step S06) and determines whetherthe update policy is satisfied. When the update policy is satisfied, instep S08, the service element 121 reads the stored firmware in the newversion from the storage unit 15 (step S081), and subsequently performsan update procedure for the execution firmware of the embedded system 1(step S082). After the update procedure is complete, the service element121 outputs a reboot instruction (step S083), the event control element131 receives the reboot instruction from the service element 121 (stepS09) and executes the reboot instruction, so as to control the microcontrol element 141 to perform a reboot procedure of the embedded system1 (step S10). In one embodiment, the micro control element 141 can be amicroprocessor.

In one embodiment, the embedded system 1 can be an informationextraction apparatus, e.g., a body-worn camera. Referring to FIG. 7, theembedded system 1 exemplified by an information extraction apparatusincludes a camera component 16, a network module 17, a processing unit18 and a storage unit 19. The processing unit 18 is coupled to thestorage unit 19 and the network module 17, and includes the foregoingautomatic firmware update system 10; that is, the processing unit 18accordingly includes the application layer 11, the middleware 12, thekernel 13 and the bootloader 14. The application layer 11 can performsteps S01, S02 and S03 through a connection between the network module17 and the remote server 2. Operation details of the middleware 12, thekernel 13 and the bootloader 14 included in the processing unit 18 areas described above, and are omitted herein. The camera component 16captures an ambient environment to generate an environment image streampresenting the ambient environment, and the camera component 16 canstore the generated environment image stream in the storage unit 19. Atthis point, a developing manufacturer of the embedded system 1exemplified by an information extraction apparatus can define an updatepolicy according to the operation of the camera component 16. Forexample, the update policy can be when the camera component 16 is notperforming a capturing operation or when the camera component 16 is notperforming a stream storage operation of storing the environment imagestream in the storage unit 19. As such, while the camera component 16performs the capturing operation and the stream storage operation, theprocessing unit 18 does not perform the update procedure of updating thefirmware to the new version; when the camera component 16 stops thecapturing operation and stops the stream storage operation, theprocessing unit 18 then automatically updates the firmware to the newversion, thus preventing the update procedure for updating the firmwareto the new version from causing a failure in capturing or storing theenvironment image stream.

In one embodiment, the storage units 15 and 19 can be two storageelements respectively having a data storage function, e.g., twonon-volatile memories. Alternatively, the storage units 15 and 19 can bedifferent data storage regions of the same storage element, e.g.,different data storage regions designated by different addresses in thesame non-volatile memory.

In one embodiment, taking an information extraction apparatus as theembedded system 1 for instance, the foregoing update policy can be whenthe camera component 16 of the embedded system 1 is not in aninformation extraction state or when the camera component 16 is notperforming an information storage operation of storing the environmentimage stream in the storage unit 15.

In conclusion, in an information extraction apparatus, and an automaticfirmware update method of an embedded system and an automatic firmwareupdate system thereof according to an embodiment, the automatic firmwareupdate system is capable of automatically downloading firmware in a newversion from a remote server and automatically performing an updateprocedure for updating firmware to the new version when an update policyis satisfied. Thus, a user of the embedded system is not required toinitiatively determine whether the firmware of the embedded system isupdated to a new version or to manually download the firmware in the newversion from the remote server, nor is the user required to contemplatea best timing for performing the update procedure for updating thefirmware to the new version. Therefore, the ease of use of the embeddedsystem is immensely enhanced, and the version of the firmware in theembedded system can be constantly kept in the latest version so as toimprove the stability of the embedded system.

While the present invention has been disclosed by way of the embodimentsabove, it is to be understood that the invention is not limited thereto.Some variations and modifications to the embodiments can be made by aperson skilled in the art without departing from the spirit and scope ofthe present invention. Therefore, the legal protection for the presentdisclosure should be defined by the appended claims.

What is claimed is:
 1. An automatic firmware update method for anembedded system, comprising: establishing wireless communication betweenan application layer of the embedded system and a remote server;detecting a version of firmware stored in the remote servercorresponding to the embedded system while the wireless communication isestablished; downloading the firmware in a new version and an updatepolicy when the firmware in the new version is available; storing thedownloaded firmware in the new version and the downloaded update policyin a storage unit; prior to starting an update procedure, issuing anupdate notification according to an update object of the downloadedfirmware in the new version; after issuing the update notification,reading the update policy according to the update notification;determining whether the update policy is satisfied, wherein the updatepolicy includes a power state of the embedded system, a datasynchronization status of the embedded system with the remote server,and an operation status of the embedded system; and in response todetermining that the update policy is satisfied, performing the updateprocedure for updating the firmware to the new version according to theread update policy.
 2. The automatic firmware update method for anembedded system according to claim 1, further comprising: receiving areboot instruction from a middleware when the update procedure iscomplete; and executing the reboot instruction to enable a bootloader toperform a reboot procedure.
 3. The automatic firmware update method foran embedded system according to claim 2, wherein the step of performingthe update procedure for updating the firmware to the new versioncomprises: reading the stored firmware in the new version; updatingexecution firmware of the embedded system according to the read firmwarein the new version; and outputting the reboot instruction after theexecution firmware is updated.
 4. The automatic firmware update methodfor an embedded system according to claim 1, wherein the step ofperforming the update procedure for updating the firmware to the newversion comprises: reading the stored firmware in the new version;shutting down the application layer; and updating execution firmware ofthe application layer according to the read firmware in the new versionafter the application layer is shut down.
 5. The automatic firmwareupdate method for an embedded system according to claim 1, wherein theupdate policy is determined to be satisfied when: the power state of theembedded system indicates the embedded system to be in a non-low powerstate; the data synchronization status indicates that the embeddedsystem is not performing data synchronization with the remote server;and the operation status indicates that a camera component of theembedded system is not performing a capturing operation or a streamstorage operation.
 6. An information extraction apparatus, comprising: acamera component, for capturing an ambient environment to generate anenvironment image stream presenting the ambient environment; a storageunit, for storing the environment image stream; a network module; and aprocessing unit, coupled to the storage unit and the network module, theprocessing unit comprising an application layer and a middleware, theapplication layer detecting a version of firmware stored in a remoteserver corresponding to an embedded system by using a network module,the application layer downloading and storing the firmware in a newversion and an update policy in the storage unit when the firmware inthe new version is available, and the middleware reading the updatepolicy upon receipt of an update notification from the applicationlayer, and after receiving the update notification, determining whetherthe update policy is satisfied, and in response to determining that theupdate policy is satisfied, performing an update procedure for updatingthe firmware to the new version according to the update policy, whereinthe update policy includes a power state of the embedded system, a datasynchronization status of the embedded system with the remote server,and an operation status of the embedded system, and the applicationlayer issues the update notification prior to the middleware startingthe update procedure.
 7. The information extraction apparatus accordingto claim 6, wherein the processing unit further comprises a bootloaderand a kernel, and the kernel receives a reboot instruction from themiddleware when the update procedure is complete and executes the rebootinstruction to enable the bootloader to perform a reboot procedure. 8.The information extraction apparatus according to claim 7, wherein theupdate procedure for updating the firmware to the new version comprisesreading the stored firmware in the new version, updating executionfirmware of the embedded system according to the read firmware in thenew version, and outputting the reboot instruction after the executionfirmware is updated.
 9. The information extraction apparatus accordingto claim 6, wherein the update procedure for updating the firmware tothe new version comprises shutting down the application layer, readingthe stored firmware in the new version, and updating execution firmwareof the application layer according to the read firmware in the newversion.
 10. The information extraction apparatus according to claim 6,wherein the update policy is determined to be satisfied when: the powerstate of the embedded system indicates the embedded system to be in anon-low power state; the data synchronization status indicates that theembedded system is not performing data synchronization with the remoteserver; and the operation status indicates that a camera component ofthe embedded system is not performing a capturing operation or a streamstorage operation.
 11. An automatic firmware update system for anembedded system, comprising: a storage unit; an application layer, forestablishing wireless communication therefrom with a remote server;wherein, the application layer detects a version of firmware stored inthe remote server corresponding to the embedded system while thewireless communication is established, the application layer downloadsthe firmware in a new version and an update policy when the firmware inthe new version is available, the application layer stores thedownloaded firmware in the new version and the downloaded update policyin the storage unit, and the application layer issues an updatenotification according to an update object of the firmware in the newversion; and a middleware, for receiving the update notification fromthe application layer; wherein after receiving the update notification,the middleware reads the update policy upon receipt of the updatenotification, determines whether the update policy is satisfied, and inresponse to determining that the update policy is satisfied, performs anupdate procedure for updating the firmware to the new version accordingto the update policy, wherein the update policy includes a power stateof the embedded system, a data synchronization status of the embeddedsystem with the remote server, and an operation status of the embeddedsystem, and the application layer issues the update notification priorto the middleware starting the update procedure.
 12. The automaticfirmware update system for an embedded system according to claim 11,further comprising: a bootloader; and a kernel, for receiving a rebootinstruction from the middleware when the update procedure is complete,and executing the reboot instruction to enable the bootloader to performa reboot procedure.
 13. The automatic firmware update system for anembedded system according to claim 12, wherein the kernel comprises anevent control element, and the event control element executes the rebootinstruction to enable the bootloader to perform the reboot procedure.14. The automatic firmware update system for an embedded systemaccording to claim 12, wherein the update procedure for updating thefirmware to the new version comprises reading the stored firmware in thenew version, updating execution firmware of the embedded systemaccording to the read firmware in the new version, and outputting thereboot instruction after the execution firmware is updated.
 15. Theautomatic firmware update system for an embedded system according toclaim 11, wherein the update procedure for updating the firmware to thenew version comprises reading the stored firmware in the new version,shutting down the application layer, and updating the execution firmwareof the application layer according to the read firmware in the newversion.
 16. The automatic firmware update system for an embedded systemaccording to claim 11, wherein the application layer comprises a networkmanagement element, and the network management element establishestherefrom wireless communication with the remote server and determineswhether the remote server has the firmware in a new versioncorresponding to the embedded system while the wireless communication isestablished.
 17. The automatic firmware update system for an embeddedsystem according to claim 11, wherein the middleware comprises a serviceelement, and the service element performs an update procedure forupdating the firmware to the new version according to the update policyupon receipt of the update notification.
 18. The automatic firmwareupdate system for an embedded system according to claim 11, wherein theupdate policy is determined to be satisfied when: the power state of theembedded system indicates the embedded system to be in a non-low powerstate; the data synchronization status indicates that the embeddedsystem is not performing data synchronization with the remote server;and the operation status indicates that a camera component of theembedded system is not performing a capturing operation or a streamstorage operation.